The MDM server must implement one or more security containers on the mobile device if the mobile device operating system is not FIPS 140-2 validated or does not use AES for data-at-rest (DAR) encryption.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-32747	WIR-WMS-MDM-02	SV-43093r1_rule	DCNR-1	Medium

Description
The encryption module in iOS 6 is not FIPS 140-2 validated, and therefore the assurance level for data encrypted using iOS does not meet DoD requirements. A third party application must be used to provide FIPS-validated encryption of sensitive DoD data to ensure it is not compromised.

STIG	Date
Mobile Device Management (MDM) Server Security Technical Implementation Guide (STIG)	2013-01-17

Details

Check Text ( C-41079r6_chk )
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy. 2. Select each security policy iOS devices are assigned to and, in turn, verify the required settings are in the policy. -Determine if the mobile operating system is FIPS 140-2 validated and uses AES encryption. Review vendor data sheets and the NIST web site. Note: iOS 5 and Android are currently (June 2012) not FIPS 140-2 validated. If yes, this check and checks WIR-WMS-GD-009-01 to WIR-WMS-GD-009-09 are not applicable. If no, complete the following procedures: -Verify the MDM product supports FIPS 140-2 validated encryption with AES. Review vendor data sheets and the NIST web site. -Verify data-at-rest and strong user authentication encryption is enabled in the security policy. (Review checks WIR-WMS-GD-009-01 to WIR-WMS-GD-009-09.) Mark as a finding if the mobile OS is not FIPS validated and the MDM agent does not contain a FIPS-validated security container.

Check Text ( C-41079r6_chk )

1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to and, in turn, verify the required settings are in the policy.

-Determine if the mobile operating system is FIPS 140-2 validated and uses AES encryption. Review vendor data sheets and the NIST web site. Note: iOS 5 and Android are currently (June 2012) not FIPS 140-2 validated.
If yes, this check and checks WIR-WMS-GD-009-01 to WIR-WMS-GD-009-09 are not applicable.
If no, complete the following procedures:
-Verify the MDM product supports FIPS 140-2 validated encryption with AES. Review vendor data sheets and the NIST web site.
-Verify data-at-rest and strong user authentication encryption is enabled in the security policy. (Review checks WIR-WMS-GD-009-01 to WIR-WMS-GD-009-09.)

Mark as a finding if the mobile OS is not FIPS validated and the MDM agent does not contain a FIPS-validated security container.

Fix Text (F-36625r2_fix)
Use an MDM product that supports FIPS 140-2 validated encryption and enable DAR encryption and strong user authentication in each security policy. Set each iOS security policy on the MDM server to enable the MDM profile.